Collecting implicit information for determining context of event actions

ABSTRACT

A device, system, and method are directed towards determining a start and/or an end time for a spontaneous event. A mobile device user creates a group for the spontaneous event, and sends the members an invite. During the event, members share media content and/or text messages with other members. Based, in part, on a flow of media content and/or text messages between the members, a determination of a start time and/or end time of the spontaneous event is automatically performed. The start time may be based on when the group is created and/or revised when a flow rate of the media content and/or messages exceed a threshold. The end time may be based on the flow rate being less than another threshold. The location of the spontaneous event may also be determined based on a location of the member&#39;s mobile devices during the event.

FIELD OF THE INVENTION

The present invention relates generally to mobile communications and,more particularly, but not exclusively to determining implicit contextdata for shared media content associated with an event.

BACKGROUND OF THE INVENTION

Tremendous changes have been occurring in the Internet that influenceour everyday lives. For example, online social networks have become thenew meeting grounds. They have been called the new power lunch tablesand new golf courses for business life in the U.S. Moreover, many peopleare using such online social networks to reconnect themselves to theirfriends, their neighborhood, their community, and to otherwise stay intouch.

The development of such online social networks touch countless aspectsof our everyday lives, providing instant access to people of similarmindsets, and enabling us to form partnerships with more people in moreways than ever before.

One aspect of our everyday lives that may benefit from online socialnetworking technology involves the aspect that social gatherings mayoften occur in a less than organized, impromptu fashion. For example,people may decide, online to get together at some restaurant, club, orthe like, almost immediately. Some social gatherings, while known bysome members of a social network may be unknown by others, until soinformed that the social event is presenting occurring, or is about tooccur.

Once at these events, people may wish to gather and share various mediacontent associated with the event. Sharing of media content has becomeprevalent on mobile devices and has changed our everyday lives. Usersare able to send and receive media content from a variety of mobiledevices. However, managing of such shared media content by multiplepeople is sometimes difficult and confusing. Therefore, it is withrespect to these considerations and others that the present inventionhas been made.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the present invention aredescribed with reference to the following drawings. In the drawings,like reference numerals refer to like parts throughout the variousfigures unless otherwise specified.

For a better understanding of the present invention, reference will bemade to the following Detailed Description, which is to be read inassociation with the accompanying drawings, wherein:

FIG. 1 is a system diagram of one embodiment of an environment in whichthe invention may be practiced;

FIG. 2 shows one embodiment of a mobile device that may be included in asystem implementing the invention;

FIG. 3 shows one embodiment of a network device that may be included ina system implementing the invention;

FIG. 4 illustrates a logical flow diagram generally showing oneembodiment of a process for creating an event for sharing of mediacontent;

FIG. 5 illustrates another logical flow diagram generally showing oneembodiment of a process for determining implicit information associatedwith the event based, in part, on the shared media content;

FIG. 6 shows one embodiment of a use case illustrating creating of anevent; and

FIG. 7 shows one embodiment of a use case illustrating sharing of mediacontent for the event, in accordance with the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present invention now will be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of illustration, specific exemplary embodiments bywhich the invention may be practiced. This invention may, however, beembodied in many different forms and should not be construed as limitedto the embodiments set forth herein; rather, these embodiments areprovided so that this disclosure will be thorough and complete, and willfully convey the scope of the invention to those skilled in the art.Among other things, the present invention may be embodied as methods ordevices. Accordingly, the present invention may take the form of anentirely hardware embodiment, an entirely software embodiment or anembodiment combining software and hardware aspects. The followingdetailed description is, therefore, not to be taken in a limiting sense.

Throughout the specification and claims, the following terms take themeanings explicitly associated herein, unless the context clearlydictates otherwise. The phrase “in one embodiment” as used herein doesnot necessarily refer to the same embodiment, though it may.Furthermore, the phrase “in another embodiment” as used herein does notnecessarily refer to a different embodiment, although it may. Thus, asdescribed below, various embodiments of the invention may be readilycombined, without departing from the scope or spirit of the invention.

In addition, as used herein, the term “or” is an inclusive “or”operator, and is equivalent to the term “and/or,” unless the contextclearly dictates otherwise. The term “based on” is not exclusive andallows for being based on additional factors not described, unless thecontext clearly dictates otherwise. In addition, throughout thespecification, the meaning of “a,” “an,” and “the” include pluralreferences. The meaning of “in” includes “in” and “on.”

As used herein, the terms “social network” and “social community” referto a concept that an individual's personal network of friends, familycolleagues, coworkers, and the subsequent connections within thosenetworks, can be utilized to find more relevant connections for avariety of activities, including, but not limited to dating, jobnetworking, service referrals, content sharing, like-minded individuals,activity partners, or the like. Such social network may be created basedon a variety of criteria, including, for example, a social event, suchas a party, meeting event, or the like.

As used herein, the term “event” refers to any social gathering ofpeople, having a start time and an end time. In one embodiment, thestart, and/or end times may be loosely established, in that they mayoccur informally, such as might arise based on an informal gathering ofpeople. In another embodiment, the event may have established startand/or end times. Moreover, in one embodiment, the event may havemultiple start/end times, such as might occur with a regularly scheduledmeeting, or the like.

As used herein, the term “spontaneous event” refers to an event thatarises from a momentary impulse, or similar impromptu action, ratherthan being planned. Thus, a spontaneous event may have either noformally announced start time, or a start time that is within a shortperiod of time from the announcement of the event. This is unlike aplanned event that has a defined start time that may occur hours or evendays after an invitation to the event is sent to a potential participateto the event. Moreover, many planned events may include a defined endtime. Often, planned events are announced with the announcementincluding a defined start and/or end time. However, because aspontaneous event may have a fuzzy or weakly defined start and/or endtimes, at least one of the times may not even be provided. For example,a spontaneous event may be where several people agree to meet around5:00 PM for a drink, but had not formally planned the meeting until oneof the potential participants suggested it during that day. Thus, whilethis example illustrates a fuzzy (around) start time, it may have nodefined end time. Another example of a spontaneous event may be where aperson sends a message to other people suggesting they meet at a party,or other event, that is currently transpiring, or is about to transpire.In this example, the start time may again be fuzzy, e.g., “let's gettogether at the party tonight.” Again, this example also illustratesthat no end time is typically announced for the spontaneous event.However, a spontaneous event may also occur within a planned event. Forexample, several people may ‘get together’ at a planned event, and‘start up’ a spontaneous event, within the planned event.

As used herein, the term “media content” refers to any digital datadirected towards a user of a computing device, including, but notlimited to audio data, multimedia data, photographs, video data, stillimages, text, graphics, animation files, voice messages, text messages,or the like.

Briefly stated the present invention is directed towards determining astart and/or an end time for a spontaneous event. The invention enablespeople to create an online membership for the spontaneous event, and toshare media content messages and/or other types of messages between themembers during the spontaneous event. In one embodiment, the mediacontent and/or other messages may be automatically posted to a websitewhere the members may then annotate the spontaneous event.

The invention enables a mobile device user to create a group thatincludes one or more members for the spontaneous event. The user maythen send the members an invite, or other message. During thespontaneous event, members may share media content messages and/or textmessages with other members. In one embodiment, based, in part, on aflow of media content and/or text messages between the members, a starttime and/or end time of the spontaneous event is automaticallydetermined. In one embodiment, the start time may be based on when thegroup is created and then revised when a flow rate of the media contentand/or messages exceed a threshold. However, other criteria may also beused to determine the start time, including, for example, when a mediacontent message is first shared. In another embodiment, a start time mayalso be determined by searching content of a text message for timeinformation, or the like. In one embodiment, the end time may be basedon the flow rate of shared messages between the members being less thananother threshold. For example, in one embodiment, if the rate ofmessages being shared indicates no messages have been shared betweenmembers for a determined amount of time, then a time that the lastmessage was shared, may be used to indicate the end time. In anotherembodiment, the end time may be determined based on a time when the rateof flow of messages being shared was less than some number of messagesper some unit of time, or the like. The location of the spontaneousevent may also be determined based on a physical location of themembers' mobile devices during the event. In addition, in oneembodiment, other implicit information may also be determined thatindicates whether a member to the group participated in the event bysending media content or other messages to other members of the groupduring the spontaneous event.

Illustrative Operating Environment

FIG. 1 shows components of one embodiment of an environment in which theinvention may be practiced. Not all the components may be required topractice the invention, and variations in the arrangement and type ofthe components may be made without departing from the spirit or scope ofthe invention. As shown, system 100 of FIG. 1 includes local areanetworks (“LANs”)/wide area networks (“WANs”)—(network) 105, wirelessnetwork 110, Event Sharing Server (ESS) 106, mobile devices (clientdevices) 102-104, and client device 101.

One embodiment of mobile devices 102-104 is described in more detailbelow in conjunction with FIG. 2. Generally, however, mobile devices102-104 may include virtually any portable computing device capable ofreceiving and sending a message over a network, such as network 105,wireless network 110, or the like. Mobile devices 102-104 may also bedescribed generally as client devices that are configured to beportable. Thus, mobile devices 102-104 may include virtually anyportable computing device capable of connecting to another computingdevice and receiving information. Such devices include portable devicessuch as, cellular telephones, smart phones, display pagers, radiofrequency (RF) devices, infrared (IR) devices, Personal DigitalAssistants (PDAs), handheld computers, laptop computers, wearablecomputers, tablet computers, integrated devices combining one or more ofthe preceding devices, and the like. As such, mobile devices 102-104typically range widely in terms of capabilities and features. Forexample, a cell phone may have a numeric keypad and a few lines ofmonochrome LCD display on which only text may be displayed. In anotherexample, a web-enabled mobile device may have a touch sensitive screen,a stylus, and several lines of color LCD display in which both text andgraphics may be displayed.

A web-enabled mobile device may include a browser application that isconfigured to receive and to send web pages, web-based messages, and thelike. The browser application may be configured to receive and displaygraphics, text, multimedia, and the like, employing virtually any webbased language, including a wireless application protocol messages(WAP), and the like. In one embodiment, the browser application isenabled to employ Handheld Device Markup Language (HDML), WirelessMarkup Language (WML), WMLScript, JavaScript, Standard GeneralizedMarkup Language (SMGL), HyperText Markup Language (HTML), eXtensibleMarkup Language (XML), and the like, to display and send a message.

Mobile devices 102-104 also may include at least one other clientapplication that is configured to receive content from another computingdevice. The client application may include a capability to provide andreceive textual content, media content, and the like. The clientapplication may further provide information that identifies itself,including a type, capability, name, and the like. In one embodiment,mobile devices 102-104 may uniquely identify themselves through any of avariety of mechanisms, including a phone number, Mobile IdentificationNumber (MIN), an electronic serial number (ESN), or other mobile deviceidentifier. The information may also indicate a content format that themobile device is enabled to employ. Such information may be provided ina message, or the like, sent to ESS 106, client device 101, or othercomputing devices.

Mobile devices 102-104 may also be configured to communicate a message,such as through Short Message Service (SMS), Multimedia Message Service(MMS), instant messaging (IM), internet relay chat (IRC), Mardam-Bey'sIRC (mIRC), Jabber, and the like, between another computing device, suchas ESS 106, client device 101, each other, or the like. However, thepresent invention is not limited to these message protocols, andvirtually any other message protocol may be employed. For example, theclient application may enable a user to interact with the browserapplication, email application, VOIP applications, or the like.

Mobile devices 102-104 may further be configured to include a clientapplication that enables the end-user to log into an end-user accountthat may be managed by another computing device, such as ESS 106. Suchend-user account, for example, may be configured to enable the end-userto receive emails, send/receive IM messages, SMS messages, accessselected web pages, participate in a social networking event, or thelike. However, participation in various social networking events mayalso be performed without logging into the end-user account.

In addition, mobile devices 102-104 may include another application thatis configured to enable the mobile user to share and/or receive mediacontent, and to display the media content. In one embodiment, each ofmobile devices 102-104 may share with and/or receive the media contentfrom ESS 106 and/or from another one of mobile devices 102-104. Forexample, media content may be shared between the mobile devices usingMMS, WAP, or the like. In one embodiment, a mobile device may receive amessage indicating the media content is available for viewing and/orannotating at a website, or the like.

In conjunction with sharing media content, mobile devices 102-104 mayenable an interaction with each other, through sharing various messages,and generally participating in a variety of integrated socialexperiences beyond merely voice communications. In one embodiment,mobile devices 102-104 may enable the interaction with a user associatedwith a spontaneous event. For example, a user of one of mobile devices102-104 may create a group that includes identified members, and send amessage to the members regarding the event. In one embodiment, membersof the group may then elect to share media content, such as photographs,video clips, audio clips, text messages, emails, or the like, with othermembers of the group. Moreover, mobile devices 102-104 may enable any ofthe members of the group to also add other members to the group. FIGS.6-7 below include one embodiment of examples of a group creation, andsharing of media content.

Mobile devices 102-104 may also communicate with non-mobile clientdevices, such as client device 101, or the like. In one embodiment, suchcommunications may include providing information about the shared mediato a user of client device 101, or the like.

Client device 101 may include virtually any computing device capable ofcommunicating over a network to send and receive information, includingsocial networking information, or the like. The set of such devices mayinclude devices that typically connect using a wired or wirelesscommunications medium such as personal computers, multiprocessorsystems, microprocessor-based or programmable consumer electronics,network PCs, or the like. In one embodiment, client device 101 may beconfigured to access a website, or other location, of shared mediacontent, and to annotate the media content, add additional mediacontent, or the like.

Wireless network 110 is configured to couple mobile devices 102-104 andits components with network 105. Wireless network 110 may include any ofa variety of wireless sub-networks that may further overlay stand-alonead-hoc networks, and the like, to provide an infrastructure-orientedconnection for mobile devices 102-104. Such sub-networks may includemesh networks, Wireless LAN (WLAN) networks, cellular networks, and thelike.

Wireless network 110 may further include an autonomous system ofterminals, gateways, routers, and the like connected by wireless radiolinks, and the like. These connectors may be configured to move freelyand randomly and organize themselves arbitrarily, such that the topologyof wireless network 110 may change rapidly.

Wireless network 110 may further employ a plurality of accesstechnologies including 2nd (2G), 3rd (3G) generation radio access forcellular systems, WLAN, Wireless Router (WR) mesh, and the like. Accesstechnologies such as 2G, 3G, and future access networks may enable widearea coverage for mobile devices, such as mobile devices 102-104 withvarious degrees of mobility. For example, wireless network 110 mayenable a radio connection through a radio network access such as GlobalSystem for Mobile communication (GSM), General Packet Radio Services(GPRS), Enhanced Data GSM Environment (EDGE), Wideband Code DivisionMultiple Access (WCDMA), and the like. In essence, wireless network 110may include virtually any wireless communication mechanism by whichinformation may travel between mobile devices 102-104 and anothercomputing device, network, and the like.

Network 105 is configured to couple ESS 106 and its components withother computing devices, including, mobile devices 102-104, clientdevice 101, and through wireless network 110 to mobile devices 102-104.Network 105 is enabled to employ any form of computer readable media forcommunicating information from one electronic device to another. Also,network 105 can include the Internet in addition to local area networks(LANs), wide area networks (WANs), direct connections, such as through auniversal serial bus (USB) port, other forms of computer-readable media,or any combination thereof. On an interconnected set of LANs, includingthose based on differing architectures and protocols, a router acts as alink between LANs, enabling messages to be sent from one to another.Also, communication links within LANs typically include twisted wirepair or coaxial cable, while communication links between networks mayutilize analog telephone lines, full or fractional dedicated digitallines including T1, T2, T3, and T4, Integrated Services Digital Networks(ISDNs), Digital Subscriber Lines (DSLs), wireless links includingsatellite links, or other communications links known to those skilled inthe art. Furthermore, remote computers and other related electronicdevices could be remotely connected to either LANs or WANs via a modemand temporary telephone link. In essence, network 105 includes anycommunication method by which information may travel between ESS 106,client device 101, and other computing devices.

Additionally, communication media typically embodies computer-readableinstructions, data structures, program modules, or other data in amodulated data signal such as a carrier wave, data signal, or othertransport mechanism and includes any information delivery media. Theterms “modulated data signal,” and “carrier-wave signal” includes asignal that has one or more of its characteristics set or changed insuch a manner as to encode information, instructions, data, and thelike, in the signal. By way of example, communication media includeswired media such as twisted pair, coaxial cable, fiber optics, waveguides, and other wired media and wireless media such as acoustic, RF,infrared, and other wireless media.

One embodiment of ESS 106 is described in more detail below inconjunction with FIG. 3. Briefly, however, ESS 106 may include anycomputing device capable of connecting to network 105 to enable creationof a spontaneous event group and for the sharing of media content withthe members of the group. ESS 106 may receive from various participantsin the event, media content, and other social networking information,including information associated with event, messages, or the like. ESS106 may then employ any of a variety of communication services to enablethe messages to be shared between the members of the group. Moreover,ESS 106 may enable a website or other location for storage and access ofat least some of the shared messages. ESS 106 further enables members ofthe group to add more members to the group, even if the member adding isnot the original creator of the group.

ESS 106 may also enable members of the group to provide annotation tothe event, and/or media content associated with the event. In oneembodiment, ESS 106 may provide a user interface, such as pull downmenus, forms, scripts, or the like, to enable a member to access eventinformation, and to provide annotations to various components associatedwith the event. For example, ESS 106 may enable a member to select aphotograph, audio clip, or other media content, using the userinterface, and to associate text, or other content to the selected item.Moreover, the user may also be enabled by ESS 106 to provide variousother metadata to the event, such as a title of the event, a location ofthe event, information about additional participants to the event, anavatar, or the like.

ESS 106 may be configured to further determine a start and/or an endtime for the event. In one embodiment, the start time and/or end time ofthe event may be automatically determined based, in part, on a flow ofmedia content and/or text messages between the members. In oneembodiment, the start time may be based on when the group is created andthen may be revised when a flow rate of the media content and/ormessages exceed a threshold. In another embodiment, the start time maybe determined by searching content of a text message for timeinformation, or the like. In one embodiment, the end time may be basedon the flow rate of shared messages between the members being less thananother threshold. In another embodiment, the end time may be determinedbased on a time when the rate of flow of messages being shared is lessthan some number per hour, or the like. ESS 106 may employ a processsimilar to that described below in conjunction with FIG. 5 to perform atleast some of its actions.

Devices that may operate as ESS 106 include personal computers desktopcomputers, multiprocessor systems, microprocessor-based or programmableconsumer electronics, network PCs, servers, and the like.

Although FIG. 1 illustrates ESS 106 as a single computing device, theinvention is not so limited. For example, one or more functions of ESS106 may be distributed across one or more distinct computing devices.For example, managing various social networking events, includingsharing of media content, managing Instant Messaging (IM) session, SMSmessages, email messages, posting of media content, determining implicitinformation such as start/end times, locations, or the like for anevent, may be performed by a plurality of computing devices, withoutdeparting from the scope or spirit of the present invention.

Illustrative Mobile Client Environment

FIG. 2 shows one embodiment of mobile device 200 that may be included ina system implementing the invention. Mobile device 200 may include manymore or less components than those shown in FIG. 2. However, thecomponents shown are sufficient to disclose an illustrative embodimentfor practicing the present invention. Mobile device 200 may represent,for example, mobile devices 102-104 of FIG. 1.

As shown in the figure, mobile device 200 includes a processing unit(CPU) 222 in communication with a mass memory 230 via a bus 224. Mobiledevice 200 also includes a power supply 226, one or more networkinterfaces 250, an audio interface 252, video interface 259, a display254, a keypad 256, an illuminator 258, an input/output interface 260, ahaptic interface 262, and an optional global positioning systems (GPS)receiver 264. Power supply 226 provides power to mobile device 200. Arechargeable or non-rechargeable battery may be used to provide power.The power may also be provided by an external power source, such as anAC adapter or a powered docking cradle that supplements and/or rechargesa battery.

Mobile device 200 may optionally communicate with a base station (notshown), or directly with another computing device. Network interface 250includes circuitry for coupling mobile device 200 to one or morenetworks, and is constructed for use with one or more communicationprotocols and technologies including, but not limited to, global systemfor mobile communication (GSM), code division multiple access (CDMA),time division multiple access (TDMA), user datagram protocol (UDP),transmission control protocol/Internet protocol (TCP/IP), SMS, generalpacket radio service (GPRS), WAP, ultra wide band (UWB), IEEE 802.16Worldwide Interoperability for Microwave Access (WiMax), SIP/RTP, or anyof a variety of other wireless communication protocols. Networkinterface 250 is sometimes known as a transceiver, transceiving device,or network interface card (NIC).

Audio interface 252 is arranged to produce and receive audio signalssuch as the sound of a human voice. For example, audio interface 252 maybe coupled to a speaker and microphone (not shown) to enabletelecommunication with others and/or generate an audio acknowledgementfor some action. Display 254 may be a liquid crystal display (LCD), gasplasma, light emitting diode (LED), or any other type of display usedwith a computing device. Display 254 may also include a touch sensitivescreen arranged to receive input from an object such as a stylus or adigit from a human hand.

Video interface 259 is arranged to capture video images, such as a stillphoto, a video segment, an infrared video, or the like. For example,video interface 259 may be coupled to a digital video camera, aweb-camera, or the like. Video interface 259 may comprise a lens, animage sensor, and other electronics. Image sensors may include acomplementary metal-oxide-semiconductor (CMOS) integrated circuit,charge-coupled device (CCD), or any other integrated circuit for sensinglight.

Keypad 256 may comprise any input device arranged to receive input froma user. For example, keypad 256 may include a push button numeric dial,or a keyboard. Keypad 256 may also include command buttons that areassociated with selecting and sending images. Illuminator 258 mayprovide a status indication and/or provide light. Illuminator 258 mayremain active for specific periods of time or in response to events. Forexample, when illuminator 258 is active, it may backlight the buttons onkeypad 256 and stay on while the client device is powered. Also,illuminator 258 may backlight these buttons in various patterns whenparticular actions are performed, such as dialing another client device.Illuminator 258 may also cause light sources positioned within atransparent or translucent case of the client device to illuminate inresponse to actions.

Mobile device 200 also comprises input/output interface 260 forcommunicating with external devices, such as a headset, or other inputor output devices not shown in FIG. 2. Input/output interface 260 canutilize one or more communication technologies, such as USB, infrared,Bluetooth™, or the like. Haptic interface 262 is arranged to providetactile feedback to a user of the client device. For example, the hapticinterface may be employed to vibrate mobile device 200 in a particularway when another user of a computing device is calling.

Optional GPS transceiver 264 can determine the physical coordinates ofmobile device 200 on the surface of the Earth, which typically outputs alocation as latitude and longitude values. GPS transceiver 264 can alsoemploy other geo-positioning mechanisms, including, but not limited to,triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS or thelike, to further determine the physical location of mobile device 200 onthe surface of the Earth. It is understood that under differentconditions, GPS transceiver 264 can determine a physical location withinmillimeters for mobile device 200; and in other cases, the determinedphysical location may be less precise, such as within a meter orsignificantly greater distances. In one embodiment, however, mobiledevice may through other components, provide other information that maybe employed to determine a physical location of the device, includingfor example, a MAC address, IP address, or the like.

Mass memory 230 includes a RAM 232, a ROM 234, and other storage means.Mass memory 230 illustrates another example of computer storage mediafor storage of information such as computer readable instructions, datastructures, program modules or other data. Mass memory 230 stores abasic input/output system (“BIOS”) 240 for controlling low-leveloperation of mobile device 200. The mass memory also stores an operatingsystem 241 for controlling the operation of mobile device 200. It willbe appreciated that this component may include a general purposeoperating system such as a version of UNIX, or LINUX™, or a specializedclient communication operating system such as Windows Mobile™, or theSymbian® operating system. The operating system may include, orinterface with a Java virtual machine module that enables control ofhardware components and/or operating system operations via Javaapplication programs.

Memory 230 further includes one or more data storage 244, which can beutilized by mobile device 200 to store, among other things, applications242 and/or other data. For example, data storage 244 may also beemployed to store information that describes various capabilities ofmobile device 200. The information may then be provided to anotherdevice, including being sent as part of a header during a communication,sent upon request, or the like. Moreover, data storage 244 may also beemployed to store media content and/or social networking informationincluding text messages, address books, group member list, or the like.At least a portion of the media content and/or event information mayalso be stored on storage medium 266, such as a disk drive, removablestorage, or the like within mobile device 200.

Applications 242 may include computer executable instructions which,when executed by mobile device 200, provide such functions as calendars,contact managers, task managers, transcoders, database programs, wordprocessing programs, screen savers, security applications, spreadsheetprograms, games, search programs, and so forth. Applications 242 mayfurther include Message Managers (MM) 245.

MM 245 represents any of a variety of applications configured totransmit, receive, and/or otherwise process messages and other networkcontent, including, but not limited to SMS, MMS, IM, email, VOIP,browsers, or the like, and to enable telecommunication with another userof another networked device. For example, MM 245 may include any of avariety of browser applications, which may be run under control ofoperating system 241 to enable and manage requesting, receiving, andrendering markup pages such as WAP pages (sometimes referred to as WAPcards), SMGL, HTML, HDML, WML, WMLScript, JavaScript, and the like.

MM 245 may further include an IM application that is configured toinitiate and otherwise manage an instant messaging session, including,but not limited to AOL Instant Messenger, Yahoo! Messenger, .NETMessenger Server, ICQ, and the like. In one embodiment, the IMapplication within MM 245 may be configured to employ a SIP/RTP tointegrate IM/VOIP features. For example, the IM application may employSIMPLE (SIP for Instant Messaging and Presence Leverage), APEX(Application Exchange), Prim (Presence and Instant Messaging Protocol),Open XML-based XMPP (Extensible Messaging and Presence Protocol), morecommonly known as Jabber and OMA (Open Mobile Alliance)'s IMPS (InstantMessaging and Presence Service) created specifically for mobile devices,or the like.

MM 245 may also include text messaging application(s) that enablesmobile device 200 to receive and/or send text messages to anotherdevice. In one embodiment, the text messaging application(s) may alsoprovide an alerting mechanism that indicates to a user of mobile device200 when a text message is received. The text messaging application(s)may also allow the user to compose a text response message, and to sendthe text response message over a network. The text messagingapplication(s) may operate to manage SMS text messages, MMS messages,Enhanced Message Service (EMS) messages, or the like, where graphics,video clips, sound files, or other media content may be communicatedbetween mobile device 200 and another networked device.

In any event, any one or more of the messaging applications within MM245 may be employed to enable a user of mobile device 200 to create agroup with members for an event, to share media content, and othermessages with members of the group, add to access media content or thelike, from another networked device, such as a website, server, or thelike. In one embodiment, MM 245 may enable a user to send SMS messages,and/or send/receive MMS messages, where the messages may include mediacontent, a link to a remote server where the media content is stored, orthe like. MM 245 may employ interfaces such as those described below inconjunction with FIGS. 6-7 to perform at least some of its actions.Moreover, mobile device 200 may employ a process such as described belowin conjunction with FIG. 4 to perform at least some of its actions.

Illustrative Server Environment

FIG. 3 shows one embodiment of a network device, according to oneembodiment of the invention. Network device 300 may include many morecomponents than those shown. The components shown, however, aresufficient to disclose an illustrative embodiment for practicing theinvention. Network device 300 may represent, for example, ESS 106 ofFIG. 1.

Network device 300 includes processing unit 312, video display adapter314, and a mass memory, all in communication with each other via bus322. The mass memory generally includes RAM 316, ROM 332, and one ormore permanent mass storage devices, such as hard disk drive 328, tapedrive, optical drive, and/or floppy disk drive. The mass memory storesoperating system 320 for controlling the operation of network device300. Any general-purpose operating system may be employed. Basicinput/output system (“BIOS”) 318 is also provided for controlling thelow-level operation of network device 300. As illustrated in FIG. 3,network device 300 also can communicate with the Internet, or some othercommunications network, via network interface unit 310, which isconstructed for use with various communication protocols including theTCP/IP protocol. Network interface unit 310 is sometimes known as atransceiver, transceiving device, or network interface card (NIC).

The mass memory as described above illustrates another type ofcomputer-readable media, namely computer storage media. Computer storagemedia may include volatile, nonvolatile, removable, and non-removablemedia implemented in any method or technology for storage ofinformation, such as computer readable instructions, data structures,program modules, or other data. Examples of computer storage mediainclude RAM, ROM, EEPROM, flash memory or other memory technology,CD-ROM, digital versatile disks (DVD) or other optical storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by a computing device.

The mass memory also stores program code and data. One or moreapplications 350 are loaded into mass memory and run on operating system320. Examples of application programs may include transcoders,schedulers, calendars, database programs, word processing programs, HTTPprograms, customizable user interface programs, IPSec applications,encryption programs, security programs, account management, and soforth. Event Manager (EM) 355 and/or Message Servers 354 may also beincluded as application programs within applications 350.

Event Data Store (EDS) 352 stores a plurality of received media content.In one embodiment, EDS 352 may be a database, a file structure, or thelike. EDS 352 may store the media content into a category structure,such as folders, albums, graphs, trees, or the like, based, in part, onevents, times associated with an event, or the like. In one embodiment,because some events may occur on a schedule, such as periodically, orthe like, media content may also be categorized based on eventschedules, or the like. Moreover, the media content may be stored usingany of a variety of data formats. In one embodiment, media contentwithin EDS 352 may be accessed for use in displaying over a network. Forexample, the media content may be accessed via a hyperlink or the like,from a web server, using a mobile device, or the like.

EDS 352 may also be configured to store information associated withgroup membership. Thus, in one embodiment, EDS 352 may receive and storeidentification information for a member to a group. Such identificationinformation may include a name, a phone number, a network address, orthe like.

Message server(s) 354 include virtually any communication server thatmay be configured to enable communications between networked devices,including email servers, SMS servers, various text messaging servers,VOIP servers, IM servers, MMS servers, RSS servers, audio servers, webservers, or the like. Message server(s) 354 may employ EDS 352 to storeor otherwise manage media content that may be communicated over anetwork. In one embodiment, various message server(s) 354 may receive amessage from one network device, and, in conjunction with Event Manager(EM) 355, employ information about group membership to store, and/orshare the media content to other members over the network. In oneembodiment, message server(s) 354, in conjunction with EM 355, storereceived media content for a group, within EDS 352.

EM 355 is configured to manage events, including spontaneous events. Assuch, EM 355 may receive from message server(s) 354 a request forcreation, deletion, or modification of a group for an event. EM 355 mayemploy EDS 352, to create and otherwise manage the membership to thegroup. EM 355 may further employ various message server(s) 354 to send amessage to the members of the group indicating that they are a member tothe group.

While message server(s) 354 may be configured to manage and enablesharing of messages, including messages having media content, EM 355 mayemploy the messages, and related information to determine implicitinformation about an event. Thus, EM 355 may determine start times, endtimes, locations of an event, or the like. EM 355 may, in oneembodiment, enable the implicit information to be accessed using atleast one of the message server(s) 354. Furthermore, EM 355 may providea user interface for use, in conjunction with various message server(s)354 to annotate an event, and/or media content within an event at awebsite, or other location. EM 355 may employ a process such asdescribed below in conjunction with FIG. 5 to perform at least some ofits actions.

Generalized Operation

The operation of certain aspects of the invention will now be describedwith respect to FIGS. 4-5. FIGS. 4-5 provide logical flow diagrams ofcertain aspects, while FIGS. 6-7 provide use case examples to furtherillustrate the invention.

FIG. 4 illustrates a logical flow diagram generally showing oneembodiment of a process for creating an event for sharing of multimediacontent. As shown, process 400 of FIG. 4 may be performed using any ofmobile devices 102-104 of FIG. 1. Moreover, in one embodiment, at leastsome of the block of process 400 may occur during an event.

Process 400 begins, after a start block, at block 402, where a user of amobile device creates a group. Referring to example 600 of FIG. 6,interface 601 illustrates that, in one embodiment, a message may be sentto an event manager service, such as EM 355 of FIG. 3, or the like. Themessage may, in one embodiment, employ SMS, however, the invention isnot so limited, and any of a variety of communication message servicesmay also be employed. As shown in FIG. 6, the message may request a“new” group to be created by the name “partygroup.” In one embodiment, afirst time user of the event manager service may also be requested toregister. Such registration, may, for example, include a click throughagreement regarding terms of service, privacy rights, or the like. Inone embodiment, the click through agreement may be accessible at aremote server, using a hyperlink, or the like.

Returning to process 400, the process flows next to block 404, where theuser of the mobile device may be asked for and/or enter identificationsfor members to the group. Referring briefly to FIG. 6, interfaces 602and 603 illustrate embodiments of possible communications that mighttranspire during block 404.

Processing then continues to block 406, where the user may then selectto send one or more messages to the members of the group. Examples ofthis are shown with interfaces 605 and 605 of FIG. 6. Process 400 maythen flow to block 408, 410, and/or block 412.

At block 408, the user that created the group or any of the members tothe group may modify the group membership. That is, anytime during anevent, a member of the group may enter an identification of anotherperson, to enable that other person to join the group and share messagesabout the event. Processing then loops to decision block 414.

At block 410, any member of the group may share media content with othermembers of the group during the event. For example, during the event, amember may take a photograph, record a video clip, audio clip, or obtaina variety of other media content. The member may then, using, forexample, MMS, or another messaging service, send the media content tothe event manager service to be shared. One example of such sharing isillustrated in FIG. 7, by interfaces 701-703. As shown, in oneembodiment, where a user may be a member to multiple groups, the usermay be asked with which group the media content is to be shared.However, in one embodiment, once selected, additional media content maybe directed to the same group, until the user selects another group, orthe termination of the event based on a determination of the end time ofthe event, or based on a variety of other actions. Also shown in FIG. 7is one example illustrating that the media content may be sent to theother members of the group using a variety of mechanism, including, forexample, MMS, or the like. In one embodiment, a message might be sent toanother member of the group as an SMS message that includes a hyperlinkto a server where the media content may be accessed. Moreover, in oneembodiment, the media content may be sent to members using a messagingservice based, in part, on a capability of their mobile device. Thus,for example, it may be determined, using, for example, informationprovided about the members' mobile devices, that one mobile device iscapable of receiving media content using MMS, WAP, email, or the like,while another mobile device may only employ SMS. In any event, mediacontent may be shared during the event, at block 410 of FIG. 4. Process400 may then flow to decision block 414.

At block 412, other types of messages may also be communicated tomembers of the group, using a variety of other text messaging services,email services, or the like. Such messages may be received anddistributed to the members of the group during the event. Processingthen flows to decision block 414.

At decision block 414, a determination is made whether there are moremessages, media content, and/or changes to the membership for thisevent. If so, processing may loop back to block 406 to continue untilthere are no more messages, media content, or changes to the membership.This looping may occur during the event, but may occur for some periodof time after the event has actually ended. For example, in someinstances, a member may have taken several photographs, video clips, orthe like, and selected to share them shortly after the event is actuallyended. Determination of the end of the event then may be based on avariety of criteria, including those described below in conjunction withFIG. 5. Briefly, however, if it is determined that no more of messagesor changes are received, processing flows to decision block 416.

At decision block 416, a determination is made whether the shared eventis to be annotated. If the shared event is to be annotated, processingflows to block 418; otherwise, processing may return to a callingprocess to perform other actions.

At block 418, in one embodiment, the user may employ their mobiledevice, or other computing device, with a browser interface to selectthe event. In one embodiment, the media content may be displayed, in aformat, suitable to the mobile device, or other computing device, suchthat the user may then select and/or annotate media content, and/or theevent itself. Referring briefly to FIG. 7, interface 705 shows oneembodiment of a website interface for displaying event informationincluding media content. The user may then employ various mechanisms,including menus, pointers, forms, text boxes, or the like, to select andprovide annotation.

FIG. 5 illustrates another logical flow diagram generally showing oneembodiment of a process for determining implicit information associatedwith the event based, in part, on the shared multimedia content. Process500 of FIG. 5 may be implemented, for example, within ESS 106 of FIG. 1.

Process 500 begins, after a start block, at decision block 502, where adetermination is made whether to establish a new group or work with anexisting group. If a new group is to be established, processing flows toblock 504; otherwise, processing proceeds to decision block 510.

At block 504, a request to create a new group is received. In oneembodiment, a candidate name for the group may be provided by a mobiledevice user. In one embodiment, if the candidate name already exists,the user may be requested to select another name. In one embodiment,however, duplication of group names may be managed based on amembership. Thus, in one embodiment, if the user is not a member of agroup having the provided name, then the group may be created with thatname, even if the group name already exists independent of the creator.Thus, in one embodiment, groups may be uniquely identified withinprocess 500 based on a creator's identification and the provided groupname. In any event, processing then continues to block 506, whereidentifiers for members to the group are received. Such identifiers mayinclude email addresses, SMS addresses, IM addresses, phone numbers, orany of a variety of other identifiers. Processing continues next toblock 508, where a time that the group is created is recorded. In oneembodiment, the time the group is created may be employed as an initialstart time for an event associated with the group. Processing then flowsto decision block 510.

At decision block 510, a determination is made whether a text message isreceived from one or more members of the group. The text message may bereceived over SMS, IM, email, MMS, or the like. If a text message isreceived, processing flows to block 512; otherwise, processing continuesto decision block 516.

At block 512, the received text message may be shared (e.g.,distributed) to the other members of the group, using any of a varietyof messaging services, including the same messaging service employedwith the received text message. Process 500 continues to block 514where, in one embodiment, an initial start time and/or end time for theevent associated with the group may be determined. For example, in oneembodiment, a time when a first text message is received for sharingwith the group may be used to determine the start time of the eventassociated with the group. In one embodiment, the contents of the textmessage may searched for keywords, such as a time, date, or the like. Ifsuch keywords are identified in the message, they may be employed, inpart, to determine the start and/or end time of the event. In anotherembodiment, information about a physical location of the mobile deviceused to send the text message may be obtained and employed to determinea location of the event. Processing flows next to decision block 516.

At decision block 516, a determination is made whether a message isreceived that includes media content. If so, processing flows to block518; otherwise, processing continues to decision block 524. At block518, the received media content may be shared (e.g., distributed) to theother members of the group. In one embodiment, the media content may beshared using a different messaging service than the media content wasreceived. Processing then moves to block 520, where the media contentmay be automatically posted to a server, such as a website, or the like,where it is associated with the event. In one embodiment, sharing of themedia content at block 518 may include providing a hyperlink, or otheraccess mechanism, to the posted location of the media content.Processing then flows to block 522, where the start and/or end time ofthe event may be revised. It is anticipated that as an event transpiresmore messages may be shared, often with an increase in a flow rate(e.g., rate of sharing) of the messages during the event. Thus, in oneembodiment, a few text messages and/or messages having media content maybe shared near a beginning of an event. However, as the event continues,it is anticipated that the rate of sharing of the messages betweenmembers increases. As the event nears an end, it is further anticipatedthat the rate of sharing of messages decreases. At some point, themessages may cease, or decrease to a very low flow rate. Thus, indetermining a revised start time for an event, various criteria may beemployed. For example, in one embodiment, when the flow rate of messagesexceeds some threshold value, such as two/minute, five/minute, or thelike, then it might be determined that the event has started. However,it should be clear that other values may also be selected, withoutdeparting from the scope of the invention. Moreover, in one embodiment,the start time may also be determined based, for example, on receiving afirst message with media content.

Similarly, the end time may also be inferred from the flow rate ofmessages. Thus, in one embodiment, when the flow rate of messages, orjust media content messages, or the like, drops below another thresholdvalue, that time, might be determined to be the end time for the event.For example, if no media content messages or text messages are receivedover a two hour period of time, 12 hour period of time, or the like,then the end time might be determined to be that time when the lastmessage was received, or based on an offset time from that time.

Moreover, during the sharing of media content messages, physicallocations of the mobile devices associated with sending of the messageto be shared may also be obtained. In one embodiment, if it isdetermined that several of the mobile devices sharing messages arewithin some determined distance apart, then those locations may be usedto determine a location of the event. Thus, in one embodiment, alocation central to the locations of the mobile devices may be used todetermine the event location. In another embodiment, the locations ofthe mobile devices may be used to search a data store, such as amerchant directory, white pages, maps, or the like, to identify afacility, business, park, theater, home, or the like. The location ofthe facility may then be employed to identify a location of the event.However, the invention is not limited to these techniques to determine alocation of the event, and virtually any other mechanism may beemployed. For example, in one embodiment, the shared messages may besearched for keywords that might indicate a location. In any event,processing then proceeds to decision block 524.

At decision block 524, a determination is made whether a request isreceived to modify the membership of the group. Such requests may bereceived from the creator of the group, or even from any one or more ofthe members of the group. In any event, if a request is received,processing proceeds to block 526 where the membership is modified.Processing then flows to decision block 528. If no such request isreceived processing also flows to decision block 528.

At decision block 528 a determination is made whether more messages arereceived for this group's event. In one embodiment, such determinationmay be made based on a flow rate of shared messages being below somethreshold. Thus, for example, if no messages are received for someperiod of time, then it might be determined that the event is ended, andprocessing flows to block 530. Although subsequent messages may bereceived, days or even weeks after an end of an event, decision block528 determines an end of an event based on some implicit informationobtainable from the sharing of the messages, as described above. Thus,if more messages are received based on the selected criteria, thenprocessing loops back to decision block 510, where it is anticipatedthat the event is currently transpiring, and more messages are to beshared, or are being shared.

At block 530, the start and/or end times for the event may be revisedusing any of a variety of mechanisms, including those described above.In one embodiment, the determined start and/or end times may be sent toa website for annotation of the event, such as illustrated in FIG. 7with start time 706 and end time 707.

Processing then flows to block 532, where the location of the event maybe revised based on any of a variety of mechanisms, including thosedescribed above. In one embodiment, the determined location may beprovided to a website for annotation of the event, such as illustratedin FIG. 7 with place 708.

Moreover, in one embodiment, a variety of other implicit information mayalso be determined based on the sharing of messages during the event.For example, in one embodiment, it might be determined based on some lowlevel of messages sent from one member, and/or a physical location ofthat member's mobile device, that that member did not attend the event.In another embodiment, such information may also be employed to indicatethat that member was present at the event, but selected not to sendmessages. Such information may also be recorded, and/or made availablefor annotation of the event, determination of future event members, orany of a variety of other uses. In any event, processing may then returnto a calling process to perform other actions.

It will be understood that each block of the flowchart illustration, andcombinations of blocks in the flowchart illustration, can be implementedby computer program instructions. These program instructions may beprovided to a processor to produce a machine, such that theinstructions, which execute on the processor, create means forimplementing the actions specified in the flowchart block or blocks. Thecomputer program instructions may be executed by a processor to cause aseries of operational steps to be performed by the processor to producea computer implemented process such that the instructions, which executeon the processor to provide steps for implementing the actions specifiedin the flowchart block or blocks. The computer program instructions mayalso cause at least some of the operational steps shown in the blocks ofthe flowchart to be performed in parallel. Moreover, some of the stepsmay also be performed across more than one processor, such as mightarise in a multi-processor computer system. In addition, one or moreblocks or combinations of blocks in the flowchart illustration may alsobe performed concurrently with other blocks or combinations of blocks,or even in a different sequence than illustrated without departing fromthe scope or spirit of the invention.

Accordingly, blocks of the flowchart illustration support combinationsof means for performing the specified actions, combinations of steps forperforming the specified actions and program instruction means forperforming the specified actions. It will also be understood that eachblock of the flowchart illustration, and combinations of blocks in theflowchart illustration, can be implemented by special purposehardware-based systems which perform the specified actions or steps, orcombinations of special purpose hardware and computer instructions.

The above specification, examples, and data provide a completedescription of the manufacture and use of the composition of theinvention. Since many embodiments of the invention can be made withoutdeparting from the spirit and scope of the invention, the inventionresides in the claims hereinafter appended.

1. A server device to manage a mobile communication, comprising: atransceiver to send and receive data over a network; and a processorthat is operative to perform actions, comprising: creating a groupassociated with a spontaneous event, wherein the spontaneous eventcomprises a gathering of people; receiving a membership to thespontaneous event, wherein each member is associated with a mobiledevice; receiving at least one text message or media content messageduring the spontaneous event; distributing to each member's mobiledevice the at least one text message or media content message during thespontaneous event, and further posting at least the media contentmessage to a website associated with the spontaneous event; anddetermining a start time and an end time associated with the spontaneousevent, based on receiving the at least one text message or media contentmessage.
 2. The server device of claim 1, wherein determining the starttime of the spontaneous event further comprises: determining the starttime based on at least one of when the first message is received or whenthe group is created; and revising the start time based on at least oneof receiving a number of text messages or media content messages thatexceed a threshold, or based on data extracted from at least one textmessage.
 3. The server device of claim 1, wherein determining the endtime of the spontaneous event further comprises: determining the endtime based on receiving less than a threshold of messages over a periodof time.
 4. The server device of claim 1, wherein the processor isoperative to perform actions, further comprising: determining a physicallocation of the spontaneous event based on a location of at least onemobile device during the spontaneous event, or from data within the atleast one text message; and posting of the physical location at thewebsite.
 5. The server device of claim 1, wherein the processor isoperative to perform actions, further comprising: receiving, from amember, information about the spontaneous event, after the end of thespontaneous event; and posting the information at the website, whereinthe information about the spontaneous event is organized based, in part,on the start or end time of the spontaneous event.
 6. Acomputer-readable medium having computer-executable instructions forsharing of event information over a network, the computer-executableinstructions when installed onto a computing device enable the computingdevice to perform actions comprising: creating a group associated with aspontaneous event, wherein the spontaneous event comprises a gatheringof people; receiving a membership to the spontaneous event, wherein eachmember is associated with a mobile device; receiving at least one textmessage or media content message during the spontaneous event;distributing to each member's mobile device the at least one textmessage or media content message during the spontaneous event; anddetermining a start time and an end time associated with the spontaneousevent, based on receiving the at least one text message or media contentmessage.
 7. The computer-readable medium of claim 6, wherein determiningthe start time further comprises determining the start time based on arate of sharing of messages exceeding a threshold.
 8. Thecomputer-readable medium of claim 6, wherein determining the end timefurther comprises determining the end time based on a rate of sharing ofmessages being less than a threshold, wherein the end time is determinedto be after the start time.
 9. A mobile device for sharing information,comprising: a memory component for storing data; and a processingcomponent for executing data that enables actions, comprising: creatinga membership group to a spontaneous event; sharing, during the event, atleast one of media content or text message to at least one other mobiledevice associated with a member of the group, wherein sharing of themedia content further comprises enabling automatic posting of the mediacontent to a website associated with the event independent of furtheractions by the mobile device; and enabling a determination of a starttime or an end time of the spontaneous event based on the sharing of theat least one media content or text message.
 10. The mobile device ofclaim 9, wherein enabling a determination of an end time furthercomprises determining the end time based on a time associated withreceiving a last message, wherein the last message is determined basedon receiving no messages for a threshold period of time for the group.11. The mobile device of claim 9, wherein the actions further comprise:enabling a determination of a location of the event based on providing aphysical location of the mobile device during sharing of messagesassociated with the event.
 12. The mobile device of claim 9, whereinsharing of the media content further comprises sending the media contentusing Multimedia Messaging Service (MMS).
 13. The mobile device of claim9, wherein enabling a determination of a start time further comprises:determining the start time for the spontaneous event based on at leastone of sharing of a first message with the members, when the membershipis created, when a number of media content messages is shared thatexceeds a threshold value, or data within the text message.
 14. Themobile device of claim 9, wherein sharing the media content furthercomprises automatically annotating the media content based at least inpart on a physicalal location of the mobile device, a time, an identityof member of the group.
 15. A method for managing a mobilecommunication, comprising: establishing a group associated with aspontaneous event, wherein each member of the group is associated with amobile device; sharing among the group during the spontaneous event atleast one of a text message or media content message using at least oneof the mobile devices; and determining a start time and an end timeassociated with the spontaneous event, based on the sharing of the textmessage or media content message.
 16. The method of claim 15, furthercomprising: modifying the membership to the group during the spontaneousevent.
 17. The method of claim 15, wherein determining the end time isbased on receiving less than a threshold of messages over a period oftime.
 18. The method of claim 15, wherein determining the start time isbased on at least one of when the first message is received or when thegroup is created, revising the determined start time based on at leastone of receiving a number of text messages or media content messagesthat exceed a threshold, or based on data extracted from at least onetext message.
 19. The method of claim 15, wherein sharing the mediacontent message further comprises sending to each member's mobile deviceat least one of the media content or a link to a location at a serverwhere the media content is accessible.
 20. A modulated data signalconfigured to include program instructions for performing the method ofclaim
 15. 21. An apparatus to manage a mobile communication, comprising:a transceiver to send and receive data over a network; means forcommunicating an occurrence of an event; means for sharing messages,including media content, during the event; means for determining a starttime and an end time of the event based, in part, on a flow of theshared messages.
 22. The apparatus of claim 21, wherein the means fordetermining the start time and the end time further comprises: means fordetermining the end time based on sharing of messages at a flow ratebelow a threshold after sharing messages at a flow rate above anotherthreshold.
 23. The apparatus of claim 21, wherein the means fordetermining the start time and the end time further comprises: means fordetermining the start time based on sharing of messages at a flow rateabove a threshold.